Multi-slicing orchestration system and method for service and/or content delivery

ABSTRACT

Aspects of the subject disclosure may include, for example, detecting a first communication device including an application based on contemporaneous access of a first service and second service functions, wherein the application communicates via first and second user data traffic flows associated with the first and second service functions. An association is facilitated of the first user data traffic flow with a first logical network slice, wherein the first user data traffic flow is conveyed by the first logical network slice. An association is facilitated of the second user data traffic flow with a second logical network slice, wherein the first and second user data traffic flows are conveyed contemporaneously by the first and second logical network slices. Other embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/590,648, filed May 9, 2017. All sections of the aforementionedapplication(s) and patent(s) are incorporated herein by reference intheir entirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a multi-slicing orchestration systemand method for service and/or content delivery.

BACKGROUND

Network providers typically offer platforms for third parties to deliverservices and applications to network subscribers. Communication networksenabled by technologies such as Network Function Virtualization (NFV)and Software Defined Networking (SDN), may be flexibly organized so asto serve various customer demands. In building advanced networks, suchas those to support future developments in wireless networks (includingnext generation, or so-called Fifth Generation (5G) wireless networks),network slicing provides the ability to create different virtualnetworks over which different traffic flows can travel isolated fromeach other. For example, a network slice can include a collection oflogical network functions that support a communication servicerequirement of a particular network service. Accordingly, differentvirtual networks, or slices, can support different services, differentusers and/or different types of user equipment (UE).

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of an example communicationnetwork for providing services to communication devices;

FIG. 2 depicts an illustrative embodiment of another examplecommunication network for providing services to communication devices;

FIGS. 3A-3B depicts illustrative embodiments of processes for managingnetwork resources used in portions of the system described in FIGS. 1and 2;

FIGS. 4-5 depict illustrative embodiments of communication systems thatprovide media services that can be used by the communication networks ofFIGS. 1-2;

FIG. 6 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 1-2, and 4-5;

FIG. 7 depicts an illustrative embodiment of a communication device; and

FIG. 8 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments for managing application of multiple logical network slicesin association with a mobile service request. In some instances, aso-called multi-slicing capability is provided on-demand. Themulti-slicing allows access to more than one logical slice, eithersequentially or in parallel, and can be based on one or more of aservice type, a quality of service (QoS), a subscriber type, etc.

Multi-slicing on demand can be obtained prior to or coincident with arequest for service. Alternatively or in addition, multi-slicing ondemand can be provided for in-session upgrades, e.g., while engaging aparticular service. In-session multi-slicing on demand can be providedwhile engaging a particular service, e.g., based on a condition, such asidentification of a specific call, a certain period of time, a selectiveuser or group of users, and/or in association with a particular event, aparticular location, according to a particular time of day,identification of an emergency, and so on.

The multi-slicing on demand can be applied according to a policy and/orprofile, e.g., enforced by a network. For example, the policy and/orprofile can be based on one or more of a premium subscription, anemergency adaptation, network conditions, e.g., capacity and/or load,geolocation, e.g., of user equipment, service availability, and so on.Other embodiments are described in the subject disclosure.

One or more aspects of the subject disclosure include device, includinga processing system having a processor and a memory that storesexecutable instructions. The instructions, when executed by theprocessing system, facilitate performance of operations that includedetecting a first mobile device including a mobile application based oncontemporaneous access of a first service function and a second servicefunction. The mobile application communicates via a first user datatraffic flow associated with the first service function and a seconduser data traffic flow associated with the second service function. Afirst logical network slice of a mobile network is identified and anassociation is facilitated of the first user data traffic flow with thefirst logical network slice of the mobile network, wherein the firstuser data traffic flow is conveyed by the first logical network slice. Asecond logical network slice of the mobile network is identified and anassociation is facilitated of the second user data traffic flow with thesecond logical network slice of the mobile network. The second user datatraffic flow is conveyed by the second logical network slicecontemporaneously with conveyance of the first user data traffic flow bythe first logical network slice.

One or more aspects of the subject disclosure include a processincluding detecting, by a processing system including a processor, afirst mobile device including a mobile application based oncontemporaneous access by a first service function and a second servicefunction. The mobile application is associated with a first user datatraffic flow associated with the first service function and a seconduser data traffic flow associated with the second service function. Afirst network slice of a mobile network is identified by the processingsystem, and an association is facilitated of the first user data trafficflow with the first network slice of the mobile network, wherein thefirst user data traffic flow is conveyed by the first network slice. Asecond network slice of the mobile network is identified by theprocessing system, and an association is facilitated of the second userdata traffic flow with the second network slice of the mobile network.The second user data traffic flow is conveyed by the second networkslice contemporaneously with conveyance of the first user data trafficflow by the first network slice.

One or more aspects of the subject disclosure include machine-readablestorage device, including executable instructions that, when executed bya processing system including a processor, facilitate performance ofoperations. The operations include detecting a first communicationdevice having an application based on contemporaneous access of a firstservice function and a second service function. The applicationcommunicates via a first user data traffic flow associated with thefirst service function and a second user data traffic flow associatedwith the second service function. A first logical network slice of acommunication network is identified and an association facilitated ofthe first user data traffic flow with the first logical network slice ofthe communication network, wherein the first user data traffic flow isconveyed by the first logical network slice. A second logical networkslice of the communication network is identified and an association isfacilitated of the second user data traffic flow with the second logicalnetwork slice of the communication network. The second user data trafficflow is conveyed by the second logical network slice contemporaneouslywith conveyance of the first user data traffic flow by the first logicalnetwork slice.

Referring now to FIG. 1, illustrative embodiments of an exemplarycommunication network for providing services to communication devices isshown. In one or more embodiments, a communications system 100 caninclude a Software Defined Network (SDN), or SDN Network 150. The SDNNetwork 150 can be controlled by one or more SDN Controllers. Forexample, the SDN network 150 can include a manager SDN controller 130,an access SDN controller 135, a Core SDN controller 140, and/or atransport SDN controller 145. The functions of the different types ofSDN Controllers 130-145 are further described below. Each SDNcontroller, such as, for example and ease of illustration, the managerSDN controller 130, can be provided by a computing system executingcomputer-executable instructions and/or modules to provide variousfunctions. In one or more embodiments, multiple computer systems orprocessors can provide the functionality illustrated and describedherein with respect to each SDN controller 130-145. To simplify thedescription of the concepts and technologies described herein, each SDNcontroller 130-145 is illustrated and described herein as being providedby a single computing system. However, it should be understood that thisexample is illustrative and therefore should not be construed as beinglimiting in any way.

In one or more embodiments, each SDN controller 130-145 can includevarious components and/or can be provided via cooperation of variousnetwork devices or components. For example, each SDN controller 130-145can include or have access various network components or resources, suchas a network resource controller, network resource autonomouscontroller, a service resource controller, a service controlinterpreter, adapters, application programming interfaces, compilers, anetwork data collection and/or analytics engine. Each SDN controller130-145 also can include or access information describing availableresources and network information, such as network object statistics,events or alarms, topology, state changes. In one or more embodiment,each SDN controller 130-145 can use and/or can generate and/or accesssystem configurations, including configurations of resources availableto the manager SDN controller 130 for proving access to services.

In one or more embodiments, the communication system 100 can include aservice-supporting portion, referred to generally as a service layer125. The service layer 125 can provide access to services and/orapplications, e.g., including third-party services and/or applicationsat a higher application layer. The service layer 125 may includecapability servers, e.g., owned by or otherwise under the direction ofan operator of the communication network 100, that can access andprovide access to application layer servers, e.g., including applicationlayer servers owned by third-party content providers via open and/orsecure Application Programming Interfaces (APIs). Alternatively or inaddition, the service layer 125 can provide an interface to a coreportion of the network referred to generally as a core network. Thecommunication network 100 can also include access to applications, suchas fixed applications and mobile applications 162A-C.

In one or more embodiments, the communication network 100 can include anSDN network 150. The SDN network 150 can include one or more SDNcontrollers 130, 135, 140 and 145 that can provide different types offunctions and can be arranged in virtual layers. For example, the SDNnetwork 150 can include a manager SDN controller 130 that controls andcoordinates functioning of the SDN network 150. The manager SDNcontroller 130 can be a top-level management system in the architecture.Below the manager SDN controller 130, a next level of SDN controllers135, 140 and 145 can be instantiated and configured by the manager SDNcontroller 130 to provide specific classes of functionality in thearchitecture. For example, the manager SDN Controller 130 can providelevel-3 functionality to control and coordinate service control,configuration, and data flow in the communication network 100. Themanager SDN controller 130 can, as needed, instantiate, configure,and/or direct level-2 SDN controllers 135, 140 and 145 for controllingaccess, core, and/or transport capabilities in the communication network100.

In one or more embodiments, the SDN network 150 can allow thecommunication network 100 to separate control plane operations from adata plane operations and can enable layer abstraction for separatingservice and network functions or elements from physical networkfunctions or elements. In one or more embodiments, the manager SDNcontroller 130 can coordinated networking and provision of applicationsand/or services. The manager SDN controller 130 can manage transportfunctions for various layers within the communication network and accessto application functions for layers above the communication network. Themanager SDN controller 130 can provide a platform for network services,network control of service instantiation and management, as well as aprogrammable environment for resource and traffic management. Themanager SDN controller 130 also can permit a combination of real timedata from the service and network elements with real-time or nearreal-time control of a forwarding plane. In various embodiments, themanager SDN controller 130 can enable flow set up in real-time, networkprogrammability, extensibility, standard interfaces, and/or multi-vendorsupport. In one embodiment, interactions between layers of thecommunication network 100 can be based upon policies to determineoptimum configuration and rapid adaptation of the network 100 tochanging state and changing customer requirements for example, predicteddemand, addition of new users, spikes in traffic, planned and unplannednetwork outages, adding new services, and/or maintenance.

In one or more embodiments, each SDN controller 130-145 can instantiatea virtualized environment including compute, storage, and data centernetworking for virtual applications. For example, the manager SDNcontroller 130 can direct on-demand instantiation of network elements,such as Virtual Network Function (VNF) elements at on-demand locationsto support network services for a customer or for the autonomous networkresource controller where capacity is needed or where backup of networkelements due to failures. Service functions can be moved and/or changedin response to traffic flow rather than traffic flow moving to thedesired service functions.

In one or more embodiments, the manager SDN controller 130 can cooperatewith a cloud orchestrator in instantiating level-2 SDN controllers135-145 and network services to support the network configuration inconnecting Virtual Machined (VMs) that the cloud orchestrator is settingup. The network instantiation and configuration can includeconfiguration of the virtual networks, which may operate at variousphysical levels in a cloud server architecture, including hypervisor,top of rack, cloud network fabric, and/or IP provider edge, which canconnect the cloud network with the service provider WAN network. In oneor more embodiments, the level-2 SDN Controllers 135-145 can cooperatewith a cloud orchestrator in instantiating VNF elements for use in, forexample, the Core Network.

In one or more embodiments, a communication device 116 can operate incommunication with and/or as a part of a communications network 100. Thefunctionality of the communication device 116 may be provided by one ormore server computers, desktop computers, mobile telephones,smartphones, laptop computers, set-top boxes, other computing systems,and the like. It should be understood that the functionality of thecommunication device 116 can be provided by a single device, by twosimilar devices, and/or by two or more dissimilar devices. For purposesof describing the concepts and technologies disclosed herein, thecommunication device 116 is described herein as a workstation orpersonal computer. It should be understood that this embodiment isillustrative, and should not be construed as being limiting in any way.

The communication device 116 can execute an operating system and one ormore application programs. The operating system can be a computerprogram that controls the operation of the communication device 116. Theapplication programs can be executable programs that are configured toexecute on top of the operating system to provide various functions.According to various embodiments, the application programs can includeweb browsers, productivity software, messaging applications,combinations thereof, or the like. In one or more embodiments, theapplication programs of the communication device 116 can includeapplications that enable interactions between the communication device116 and other devices or entities. In some contemplated embodiments, theapplication programs can provide functionality for interacting withand/or communicating with the communication network 100 and, in turn,having communications analyzed by the manager SDN controller 130 or,alternatively, any of the SDN Controllers 130-145 in the SDN network150.

According to various embodiments, the SDN network 150 can include and/oraccess resources, such as a service orchestrator, a software definednetwork controller, a cloud orchestrator, and/or other elements. Itshould be understood that the manager SDN controller 130, and any of theabove-described components, or combinations thereof, may be embodied asor in stand-alone devices or components thereof operating as part of orin communication with the communication network 100. As such, theillustrated embodiment should be understood as being illustrative ofonly some contemplated embodiments and should not be construed as beinglimiting in any way.

In one or more embodiments, the SDN network 150 can automaticallyevaluate application service requirements that have been requested fromthe communication system 100. In one embodiment, a service request canbe received from a subscriber, or customer, or customer device. Forexample, a request can be receive via a portal. The service request canbe provided to the soft manager SDN controller 130 for service creation,instantiation, and management. According to various embodiments, theservice request can be analyzed by the manager SDN controller 130. Inone embodiment, the manager SDN controller 130 can access or query theservice layer 125 to determine service requirements needed forfulfilling the service request.

In one or more embodiments, a service request can be received byequipment of a subscriber or customer (e.g., via the portal), andprovided to the SDN network 150 for service creation, instantiation, andmanagement. The service request can include application objects and/orrequests for particular services or functions. Thus, the service requestcan include objects that define service functions that are desired,requests for generation of services and/or requests for particularfunctionality, queries, combinations thereof, or the like. It should beunderstood that these examples are illustrative and therefore should notbe construed as being limiting in any way. According to variousembodiments, the service request can be analyzed by the SDN controller130-145 and a set composed of a directed graph and the associated modelor model files are selected. The model can define features of theservice and can generate in a programming language or format such asXML, Yang models, other types of files, combinations thereof, or thelike. The selected directed graph can be used at runtime to fill in theevent-specific details from the API, the resource allocations per thedirected graph and the resource model, and one or more state changes inthe network through the adapters.

In one or more embodiments, the communication device 116 can communicatewith the communication network 100 via a wireless communication link.For example, the communication device 116 can be a mobile communicationdevice 116 that communications via a cellular communication link througha Radio Access Network (RAN) technology. A mobility network 117, such asa 3GPP wireless network, e.g., an LTE network or a 5G network, canestablish wireless communications with the communication device 116,where the communication device 116 can move from cell to cell, whilemaintaining a communication session. In another example, thecommunication device 116 can communication with the communicationnetwork via a non-3GPP wireless link, e.g., a WiFi network link. TheWiFi network can be, for example, a local area network (LAN) that issupported by a router capable of wireless communications or can be anindividual device, such another mobile communication device 116 capableof acting as an intermediary (e.g., a Hot Spot). In one or moreembodiments, the communication network 100 can be a converged networkcapable of supporting a wide range of access, core and transportnetworks, such as wireline, wireless, satellite, 3GGP, non-3GPP, and/or5G. It is understood that the radio frequency spectrum used in wirelessaccess can include licensed spectrum, unlicensed spectrum andcombinations thereof.

In one or more embodiments, a Management Gateway (MGW) 142 can beincluded in the communication network 100. The MGW 142 can capturetraffic entering the communication network 100 from variouscommunication devices 116 and/or various Access Networks (AN) 117. TheMGW 142 can communicate with the SDN network 150, e.g., with the managerSDN controller 130, regarding traffic entering the communication network100. In one embodiment, the MGW 142 and the manager SDN controller 130can communicate via a communications protocol, such as an OpenFlow®protocol that provide access to a forwarding plane of a network device,such as a switch or router, over a network. OpenFlow® is a registeredtrademark of the Open Networking Foundation of Palo Alto, Calif. The MGW142 can inform the management SDN controller 130 of informationregarding services sought by one or more communication devices 130. Themanagement SDN controller 130 can analyze these services to determineservice functions and/or network data flows that would be required tofacilitate delivery of these services to the communication devices 116.

In one or more embodiments, the manager SDN controller 130 can query theservice layer 125 to determine the functional and/or resourcerequirements to provide the service to the communication device 116. Inone or more embodiments, the service requirements can include servicefeature data. In one or more embodiments, this service feature data canbe generated by or provided to the service layer 125 and/or the managerSDN controller 130 via interactions between the communication device 116and the portal. For example, in the process of making the servicerequest, the communication device 116 can make a series of selectionsfrom menus, drop-down lists, fields, tables, or other data or objectselection mechanisms that may be provided by the portal and/or theapplication programs executing on the communication device 116. In someembodiments, the application programs can include a web browserapplication and/or other application that can obtain data from theportal. In one or more embodiments, the application programs can use thedata to generate and present a user interface at the communicationdevice 116. The user interface can include possible service features,and a user or other entity can select the desired features, drag anddrop desired features, and/or otherwise indicate desired features in aservice.

In one or more embodiments, the manager SDN controller 130 can analyzepolicies or policy defined for a service. This policy can includenetwork engineering rules, which can be defined by a network designer,engineer, business unit, operations personnel, or the like, or asubscriber policy, which can be defined during ordering of the service.Subscriber policies can include, for example, service level agreements(“SLAs”), location restrictions (e.g., locations at which the servicesare allowed or not allowed), bandwidth ranges, time restrictions (e.g.,times of day, days of week, or other times at which the service isallowed or not allowed), security restrictions or policies, combinationsthereof, or the like.

In one or more embodiments, the manager SDN controller 130 can determinefrom the service model one or more physical network functions or otherresources that will be needed or used to support the service. Themanager SDN controller 130 also can analyze the service model toidentify one or more virtual network functions or other functions thatwill support or provide the features of the service. The manager SDNcontroller 130 also can determine, via analysis of the service model,process flows between the various resources and/or functions used tosupport or provide the service features.

In at least some embodiments, the SDN network 130 implements a multiplelevel, dynamic design by which the manager SDN controller 130 of the SDNnetwork 150 can automatically prioritize and instantiate a next lowerlevel (e.g., level-2) SDN controller including one or more of an accessnetwork SDN controller 135, a core network SDN controller 140, and/or atransport network SDN controller 145. It is understood that such actionscan be undertaken on the fly, e.g., at runtime, responsive to networkactivity, responsive to particular requests, in a course of normalnetwork operations, configuration, management, and the like. Generally,the manager SDN controller 130 can instantiate at least one set of theselevel-2 SDN controllers 135-145 to provide baseline functionality andconnectivity for a least one communication device 116. As serverrequests are processed, the manager SDN controller 130 can evaluate theservice request requirements, i.e., the service features, and comparethe required resources and capacities for these resources with theresources and capacities currently available at the SDN network 150 viathe level-2 SDN Controllers 135-145.

In one embodiment, the manager SDN controller 130 can communicate witheach of the instantiated SDN controllers 135-145 via a communicationinterface, such as an interface that applies OpenFlow® data networkprotocols. In addition, the SDN controllers 135-145 of level-2 to cancommunicate among themselves to determine resource capabilities,capacities, shortages, failures, and/or warnings. In one or moreembodiments, if the manager SDN controller 130 determines that therequested service can be performed, within system margins, using thecurrently instantiated SDN controllers 135-145, then the manager SDNcontroller 130 can decide to direct the SDN controllers 135-145 toperform the service for the communication device 116. Alternatively, ifthe manager SDN controller 130 determines a shortage or shortfall in aneeded resource, then the manager SDN controller 130 can directinstantiation of one or more new SDN controller 135-145 to perform allor part of the requested service. For example, the manager SDNcontroller 130 may determine that the service request associated withthe example communication device 116, or many communication devices 116,or merely received at the communication network 110 from anindeterminate device (e.g., a request for resources from anothernetwork) requires additional core SDN controller capacity 140. In thiscase, the manager SDN controller 130 can direct the instantiation ofadditional core SDN controller 140 capacity from a set of configurableSDN controller devices at the cloud.

In one or more embodiments, level-2 SDN Controllers 135-145, includingaccess SDN controller 135, core SDN controller 140, and transport SDNcontroller 145 can control devices at an upper level, e.g., level-1, ofthe communication network 100. For example, the access SDN controller135 can control, direct, configure, and monitor access resources 117 and119 for the network 100, such as eNodeB controllers, RAN controllers,and or WiFi controllers. In another example, the core SDN controller 140can control, direct, configure, and monitor core resources 174A-176C forthe core network of the communication network 100, such as Gateways (GW)for Control Plane (CP) 174A-C, User Plane (UP) 176A-C, and/or legacy(i.e., combined user and control plane). In another example, thetransport SDN controller can control, direct, configure, and monitortransport layer services 154, such as a Multiprotocol Label Switching(MPLS) network, Fiber Optics network, and/or a Backbone network.

In one or more embodiments, the manager SDN controller 130, adapted tosupport level-3 functionality, can manage one or more sets of level-2SDN controllers 135-145 in the SDN network 150. The manager SDNcontroller 130 can configure and/or reconfigure the instantiated SDNcontrollers 135-145 to optimize the SDN network 150 according to loadingcreated by the service requests. For example, the manager SDN controller130 can invention automatically instantiate multiple levels of fullydistributed SDN controllers 135-145. Likewise the level-2 SDNcontrollers 135-145 can instantiate and/or configure and/or reconfigureVNF elements 174A-176C at level-1. Each of the SDN controllers 130-145can support instantiation “on the fly” based on new requests, the endingof old requests, monitoring network traffic, and/or requesting loadinginformation from any of the other SDN controllers 135-145 and/or the VNFelements 174A-176C.

For example, the manager SDN controller 130 can instantiate and/ordecommission SDN controllers 135-145 into and out from the SDN network150 on an on-going basis according to the exchange-to-exchange (E2E)application service requirements. Similarly, the SDN controllers 135-145can instantiated and/or decommission and/or reconfigure VNF elements174A-176C. For example, in a streaming media application, such as aNetflix™ Video Delivery application, the manager SDN controller 130 candetermine that network demands for the access SDN controller 135 andtransport SDN controller 145 may be relatively large for a given set ofcommunication devices 116, while the core SDN controller 140 demands forthese communication devices 116 may be relatively normal. The managerSDN controller 130 can look at the available resources and capacitiesfor the currently instantiated SDN controllers 135-145 that are supportthese communication devices 116. If the demands of the media streamingapplication exceed the available resources, then the manager SDNcontroller 130 can automatically address the issue by, for example,instantiating additional access SDN controller 135 and transport SDNcontroller 145 resources.

In one or more embodiments, the manager SDN controller 130 may determinethat sufficient resources exist at the currently instantiated access SDNcontroller 135 and transport SDN controller 145 resources, however, thepriorities of these resources need to be adjusted. For example, where aheavy streaming media loading is identified, the access SDN controller135 and transport SDN controller 145 resources may be given higherpriority in comparison to the core SDN controller 140. Conversely, if aheavy loading of Voice over IP (VoIP) services is identified, then themanager SDN controller 130 can automatically place the core network SDNcontroller 140 into higher priority in comparison to access network SDNcontroller 135 and transport network SDN controller 145.

In one or more embodiments, a SDN-controlled network, using networkfunction virtualization, software defined networking, and/or cloud-basedconcepts, can provide flexibility in number, type and/or configurationof virtual networks, sometimes referred to as flexible network slicing.Network slicing facilitates distributed functionality, e.g., to supportdiverged types of services and requirements, such as those supportingfuture developments in wireless networks including 5G networks. SDNcontrollers 130 can provide control and configuration to supportdifferent network slices on appropriate network slices or clouds 162A-Cby instantiating and controlling a proper sets of VNF elements 174A-176Cand by the optimal distribution of these VNF elements 174A-176C based onapplication and service requirements.

Generally speaking, network slicing is a network management technique inwhich compute and/or connectivity resources in a communications networkare divided to create a set of different virtual networks. For example,network slices can be supported by virtual network functionsinstantiated upon generic computing resources to provide specificnetwork functions. Without limitation, network slices can be used in oneor more of a core network, a radio access network, a backhaul network.Isolation provided by the network slices can be applied to differentoperators, different types of services, different types of networktraffic, different users and/or classes of users, and the like.

In one or more embodiments, network slicing can be used by the SDNnetwork to support multiple virtual networks behind the air interface(s)117 of the communication network. The slicing of the network intomultiple virtual networks can provide optimal support for differentRadio Access Networks (RAN) and/or different service types runningacross a single RAN. Further, in one or more embodiments, flexibledistribution of the access, edge, and core elements of the network cloudcan provide optimal support regarding latency and/or service isolationfor different apps and service requirements. Connectivity betweencomputing resources can be allocated so that traffic of one slice can beisolated from that of another. Isolation can be based on one or more ofnetwork operator, service, application, user, user equipment, level ofsubscription service, and so on. By way of example, one slice can beconfigured to suit the needs of a Machine Type Communication (MTC)service, which typically generate large numbers of short transmissionsthat do not require ultra-reliable connections. Another slice cansupport Mobile Broadband (MBB), or enhanced Mobile Broadband (eMBB)services, having different requirements. Network slices created to servethe needs of different services may be built upon the resourcesallocated to a network operator within a slice that isolates the networkoperator from other network operators on a set of resources associatedwith a service provider.

In one or more embodiments, the SDN Network 150 can determine whatservice(s) is being used and which external network and/or networkoperator, e.g., by way of an Access Point Node (APN), is being used forthe specific traffic. In one embodiment, the analysis can be performedby a SDN controller 130-145, which derive information either directlyfrom communications entering the network 100 form one or morecommunication devices 116 or from a MGW 142 that is monitoring this typeof traffic. In one or more embodiments, a SDN Controller 130 can performanalysis that determine a detailed granularity of the specific servicesbeing sought by or provided to the communication device 116. Thisdetailed granularity can reveal sets of service functions (e.g.,identifying servers, providing connections to applications, verifyingauthenticity, providing control plane and user plane functions) that arenecessary for facilitating the delivery of services. The detailedgranularity can also include determining various data pathways, withinthe network 100 and beyond, necessary for facilitating the delivery ofservices. The SDN Controller 130 can instantiate VNF elements 174A, 176Athat can cause traffic to be sent to respective destinations such as 4G,4G+, or 5G APNs, based upon breaking up the specific services requestedinto the types of service functions, resources, data accesses, and/ornetwork data paths. The VNF elements that are composed, configured, andchained by the SDN Controller 130 for implementing the necessary servicefunctions are, in turn, instantiated into the 5G network 100 in networklocations that optimize one or more characteristics of the servicefunctions and/or network data paths.

Examples of flexible, adaptive networks, such as the illustrativeexample communication network 100, are disclosed in commonly owned, U.S.patent application Ser. No. 15/344,692, entitled “Method and Apparatusfor a Responsive Software Defined Network,” filed on Nov. 7, 2016, andincorporated herein by reference in its entirety. Additionally,techniques related to dynamic network routing in a software definednetwork are disclosed in U.S. patent application Ser. No. 15/351,618,entitled “Method and Apparatus for Dynamic Network Routing in a SoftwareDefined Network,” filed on Nov. 15, 2016, and also incorporated hereinby reference in its entirety.

FIG. 2 depicts an illustrative embodiment of another examplecommunication system 200 for supporting applications and/or services tofixed and/or mobile user equipment (UE). The communication system 200includes a first mobility network 201 that provides access toapplications and/or services to mobile communication devices 202 a, 202b, generally 202. In some embodiments, the communication system 200 caninclude other mobility networks, such as a second 5G mobility network226, e.g., of a competitor. The first mobility network 201 usesmanagement gateways 204 a, 204 b, generally 204, to capture trafficentering the communication network 201 from various UE 202 and variousaccess networks 205 a, 205 b, generally 205. The management gateway 204can communicate with a software defined network, e.g., in cooperationwith an SDN controller 210, regarding traffic entering the firstcommunication network 201. In one embodiment, the management gateway 204and the SDN controller 210 can communicate via a communicationsprotocol, such as an OpenFlow® protocol that provide access to aforwarding plane of a network device, such as a switch or router, over anetwork. The management gateway 204 can inform the SDN controller 210 ofinformation regarding application services sought by the one or more UEs202. The SDN controller 210 can analyze these application servicerequests to determine service requirements, e.g., service functionsand/or network data flows that would be required to facilitate deliveryof the requested application services to the UE 202. These analyses canbe accomplished by the SDN controller 210 alone, or in combination withone or more of a service layer 208 and/or the management gateway 204.

In at least some embodiments, the first mobility network 201 includesmultiple network clouds, or slices 212 a, 212 b, 212 c, generally 212.Network slices 212 can be supported by virtual network functions thatare instantiated upon generic computing resources to provide specificnetwork functions. Network slices 212 can be created, configured, used,reconfigured, and in at least some instances decommissioned or retired,as needed to serve the needs of one or more requested services. In atleast some network architectures, such as 5G, each network slice 212 canbe adapted to separate control plane operations from user planeoperations, e.g., by separately processing control or signaling planetraffic and user or data plane traffic. Generally speaking, the controlplane traffic can be used to access, coordinate and/or otherwise manageestablishment and/or usage of the user plane traffic. Separation of thecontrol plane from the user plane within a network slice allows thecontrol plane to coordinate updates, modifications or changes to userplane traffic being processed by the network slice.

In some embodiments, the first mobility network 201 includes a defaultnetwork slice 206, sometimes referred to as a main slice. The defaultslice 206 can be established during attachment and/or activation of a UE202 to the mobility network, similar in at least some sense to a defaultbearer established in 4G LTE networks. The default slice 206 can beassociated with a UE 202 when the UE 202 is first powered on withincommunication range of an access network 205 a of the mobility network201. Alternatively or in addition, the default slice 206 can beestablished, allocated to or otherwise associated with the UE 202 a whenthe UE 206 a roams into the communication range of the access networkand/or is a subject of a handover from another access network 205 b,including other access networks of the same mobility network 201 orother mobility networks 226. Other mobility networks 226 can includeanother mobility network 226 of a common mobility network serviceprovider, e.g., according to a different architecture, such as 2G, 3G,4G. Alternatively or in addition, other mobility networks 226 caninclude networks of a different network service provider, includingnetworks of a similar, e.g., 5G, and/or different architecture.

The network slices 212, once provisioned, can facilitate access by theUE 202 a to applications and/or service functions. The applicationsand/or service functions can include network functions provided by anetwork service provider, other service provided by a service providerthat may be the same or different from the network service provider. Inat least some instances, the application and/or service can be providedover the top, e.g., by a third party independent from either the networkservice provider or the service provider. The illustrative exampleincludes an example application 222 that can be accessed via theresources of the mobility network 501 according to the network slicingtechniques disclosed herein.

In general, access can be facilitated by a service layer 208. Theservice layer 208 is configured to facilitate access to services and/orapplications, e.g., including third-party services and/or applications222 at a higher application layer. The service layer 208 also providesan interface to a core portion of the network referred to generally as acore network.

It is understood that in some scenarios, a service is provided to asingle user equipment (UE) 202 a. Examples include services that can bedelivered by a network source, such as mobile television, video ondemand, web surfing, mail service, and the like. Alternatively or inaddition, the service can include more than one UE 202 a, 202 b.Examples of multi-UE services can include, without limitation, voicecalling, e.g., VoIP, video conferencing, messaging, gaming, and thelike, that engage the multiple UEs 202 a, 202 b in a common or otherwiseshared application and/or service.

One or more of network access and/or services access can be based on oneor more of a service type, a quality of service (QoS), a subscribertype, a level of subscription, and the like. A first subscriber maysubscribe to a voice service without messaging and/or without ahigh-quality video service, whereas a second subscriber may subscribe tothe same voice service and the high-quality video service. Informationrelated to and/or indicative of subscribed services can be include in apolicy and/or rules. Such policies or rules can include, withoutlimitation, network policies, subscriber and/or equipment policies.Network policies can include one or more of network engineering rulesthat can include policy type rules imposed by a network operator,regulatory rules imposed by a regulating body, and/or equipment basedrules on physical network resources. Subscriber policies can beassociated with each particular subscription. Examples include ServiceLevel Agreements (SLA) that identify obligations of a network and/orservice provider based on a particular level of subscription. Subscriberpolicies can include, without limitation, location restrictions (e.g.,locations at which the services are allowed or not allowed), bandwidthranges, time restrictions (e.g., times of day, days of week, or othertimes at which the service is allowed or not allowed), securityrestrictions or policies, data limits, combinations thereof, or thelike.

As network slices 212 can provide access to different services,applications and/or levels of service, it is understood that access tocertain network slices can be allowed and/or restricted based on any ofthe foregoing policies. Accordingly, one or more of the SDN controller210, the management gateways 204 or the service layer 208 identifiespolicies that apply to delivery of services and/or access to networkslices.

It is understood that one or more of the access networks 205 and/or theother mobility networks 226 can include operation within licensedportions of the radio frequency spectrum. Such licensed operationincludes 3GPP networks, such as 2G, 3G, 4G, and 5G. It is furtherunderstood that one or more of the access networks 205 and/or the othermobility networks 226 can include operations within unlicensed portionsof the radio frequency spectrum. Such unlicensed operations can include3GPP networks supporting unlicensed spectrum operation, e.g., 5G and/orother non-3GPP architectures, such as IEEE 802.11 wireless networks,WiFi, Bluetooth, and so on.

The example mobility network 201 includes a group of network slices,including a first network slice 212 a, that supports a first mobileapplication service requirement, a second network slice 212 b thatsupports second and third mobile application service requirements, and athird network slice 212 c that supports a fourth mobile applicationservice requirement. Each of the mobile devices 202 and the networkslices 212 a, 212 b, 212 c, generally 212, is in communication with atleast one of the management gateways 204.

The SDN Controller 210 alone or in combination with the service layer208 can instantiate the first network slice 212 a, such as VNF elements214A, 216A, respectively supporting control plane operations and dataplane operations. The VNF elements 214A, 216A can cause control planeand/or user plane traffic to be sent to respective destinations such as4G, 4G+, or 5G APNs, based upon breaking up the specific servicesrequested into the types of service functions, resources, data accesses,and/or network data paths. Likewise, second and third network slices 212b, 212 c are instantiated using VNF elements 214B, 214C, 216B, 216C. TheVNF control plane elements 214A, 214B, 214C, generally 214 and the VNFuser plane elements 216A, 216B, 216C, generally 216, can be composed,configured, and/or chained by the SDN Controller 210 and/or the servicelayer 208 for implementing one or more corresponding service functions.The VNF elements 214, 216 are, in turn, instantiated into the 5G network210 in network locations that facilitate one or more characteristics ofthe service functions and/or network data paths.

It is understood that some network slices 212 provide multiple servicefunctions, wherein each service function can be provided according to apredetermined requirement, such as a minimum acceptable level ofservice, above some minimum threshold requirement, e.g., quality,reliability, packet loss, error rate, signal level, delay, bandwidth, orthe like. It is understood that some embodiments, a service requested bya UE 202 may include multiple, different services. The multipledifferent services may be dependent on the user application, such as ahome security service that may provide streaming video of a user's hometo a mobile device of the user, as well as message service to a securityoperations center and/or local emergency services, such as police orfire. Other examples include, without limitation, health careapplications, such as connected care applications that monitor biometricinformation of a user, evaluate the user's physical condition based onthe monitored data, provide reporting to supervising physicians and/ormedical centers, and in at least some instances, contact emergencyservices upon detection of a medical emergency. The example networkincludes example connected care slices 220 a, 220 b, generally 220,configured to support delivery of such services. It is understood thatcertain features of the different services, video versus text messaging,can be satisfied by different network connectivity, such as differentbandwidths, different reliabilities, and the like.

Although video of a home security system may require a greater bandwidththan text messaging, the video service can be acceptable when subject toshort delays and/or interruptions. Consider another application in whicha first surgeon is performing an operation in consultation with othersurgeons at a remote location by way of a mobile application. Theapplication may include video services, e.g., reflecting progress of theoperation, as well as voice services and/or messaging services. Stillother services can include data exchange services, e.g., to allow forremote monitoring and/or control of medical devices. It is apparent thatnetwork resources designated for the latter example would require a muchgreater degree of reliability, and perhaps bandwidth, and the like.

In at least some instances, it can be left up to network serviceproviders to determine how network resources are configured and sharedaccording to network slicing. To this end, it is understood that somenetwork slices can be general, in at least some sense, providing morethan one service, such as video, voice and/or text messaging, toaccording to a first set of service requirements, whereas other networkslices can be specific, e.g., dedicated to a single service and/or groupof services. Alternatively or in addition, other network slices thataccommodate multiple services can do so to a different set of servicerequirements.

Continuing with the example, a first UE 202 a can attach to the first 5Gnetwork 201, being associated with a default slice 206. The first UE 202a can initiate a service request for service creation, instantiationand/or management. The request can be submitted to a first managementgateway 204 a that captures traffic entering the communication network501 from the first UE 202 a. Upon initial request (A) from subscriber UE202 a, the management gateway 214 a forwards the service request to theservice layer 208, e.g., via the default slice 206 (B). The servicelayer 208 can include a service layer cloud network configuration. Oncethe service and service requirements, e.g., QoS, and subscriber type,e.g., enterprise, individual, have been identified, the service layer208 sends a command to the SDN Controller 210 (C) and/or the managementgateway 204 a to associate the correct slice 204 a (D) to establish aforwarding of traffic, both control plane and user plane (E), to thecorrect slice 212 a.

The SDN controller 210 accesses or queries the service layer 208 (C) todetermine service requirements needed for fulfilling the servicerequest, including determining any functional and/or resourcerequirements to provide the service to the UE 202 a. The SDN controller210 alone or in combination with one or more of the management gateway202 a and/or the service layer 208, analyzes any related policies. Thiscan include any of the foregoing policies, e.g., network policies,subscriber policies, SLAs, and the like. The SDN controller 210instantiates, configures and/or reconfigures VNF elements of a networkslice 212 a (D). In at least some embodiments, the VNF elements can becomposed, configured and/or combined, e.g., chained, for implementingthe appropriate service functions. It is understood that the processdetermines a detailed granularity of the specific services being soughtby the UE 202 a. The detailed granularity can reveal sets of servicefunctions (e.g., identifying servers, providing connections toapplications, verifying authenticity, providing control plane and userplane functions) that are necessary for facilitating the delivery ofservices. In the illustrative example, the requested service can includenetwork access (E) to the application 222 via the first network slice212 a.

FIG. 3A depicts an illustrative embodiment of processes 300 for managingnetwork resources used in portions of the system described in FIGS. 1and 2. A request for service is received or otherwise detected at 302.The request for service can be initiated by a communication device, suchas a UE 202 (FIG. 2), and/or via another location, such as a web site orportal. It is understood that the request can include an initialrequest, e.g., a first request from a recently attached UE 202 and/or anew request from a previously attached UE. Alternatively or in addition,the request can include a request for a change to an existing service,e.g., in a dynamic sense, as in an upgrade to a lever of service. By wayof example, an upgrade might include a small-screen video streamingservice to a large-screen or high resolution video streaming service.Alternatively or in addition, an upgrade might include adding streamingvideo to an existing VoIP call to provide a videoconferencing service.

The service requirements are identified at 304 based on the servicerequest. In at least some embodiments, the request for service caninclude one or more application objects and/or requests for particularservices or functions. Such service feature data can be generated by orprovided to a service layer 208 and/or an SDN controller 210 (FIG. 2)via interactions between the UE 202 and/or the portal. The servicefeatures can include requirements of a subscriber and/or a particular UEdevice. Without limitation, example service features include anidentification of a service type, e.g., security, authentication,streaming media, a related QoS, a subscriber type, e.g., an enterprisesubscriber or an individual user, and the like.

A first logical network slice is identified at 306 based on servicerequirements. The first network slice can be a pre-existing slice 212 orgroup of slices. Such pre-existing slices may have already beeninstantiated for prior usage by the same subscriber associated with therequesting UE. Alternatively or in addition, pre-existing slice(s) mayhave been instantiated previously in anticipation of similar requests,or responsive to similar request from other UEs and/or subscribers. Inat least some embodiments, the first slice can include multiple slices,e.g., in a chained arrangement, as may be required to satisfy therequested service.

A determination is made at 308, as to whether the service requirement issatisfied by the first logical network slice(s). To the extent that theservice requirement has been satisfied, the first logical network sliceor group of slices are selected and/or assigned to the service requestat 310. Network traffic, including control plane and user plane traffic,are forwarded by way of the selected and/or assigned slice(s) at 316. Itis understood, generally, that separation of the control plane from theuser plane allows the control plane to facilitate a re-configurationand/or change of a slice(s) already forwarding user traffic, withoutinterrupting the forwarding of the user traffic. User traffic can beredirected and/or modified as required after any reconfigurationcoordinated by the control plane.

To the extent that the service requirement has not been satisfied, asecond network slice or group of slices can be identified at 312. Thesecond network slice(s) can be identified based on the original servicerequirements or on a subset of the original service requirements thatare not satisfied by the first network slice(s). Identification of thesecond slice(s) can be accomplished by one or more of the service layer,the SDN controller, the management gateway, e.g., as disclosed above.

Once identified, the second network slice(s) can be selected and/orassigned at 314 to fulfil all or part of the requirements of therequested service. In some embodiments, the first network slice(s)handle first portion of control plane and/or user plane traffic, whilethe second network slice(s) handle a second portion of the control planeand/or user plane traffic associated with the same requested service bythe same UE. For example, if a requested service requires servicefunctions A+B+C, and the first network slice(s) can provide A+B but notC, then the second network slice(s) can be employed to provide servicefunction C, such that collectively, the first and second network slicesprovide all three types of service functions.

Alternatively or in addition, it may make sense to allow the secondnetwork slice(s) to provide all of the service functions, e.g., A+B+C,instead of sharing functions across the first and second network slices.In this example, the second network slice(s) can be used instead of thefirst network slice(s). To the extent this occurs during an initialrequest for service, it is possible that the first network slice(s) donot carry any related traffic. To the extent this occurs dynamically,e.g., during a delivery of services to the UE using the first networkslice(s), then the control plane can be used to transfer all traffic tothe second network slice(s). To the extent that a traffic flow of thefirst network slice(s) are modified, the first network slices can bere-configured and/or decommissioned.

In an alternative scenario, the first network slice(s) can bereconfigured to change from providing service functions A+B to providingonly service function A, while allowing the second network slice(s) toprovide service functions B+C. It is understood that other scenarios arepossible in which traffic can be initially established and/ordynamically re-configured on one or more different network slices.

It is further understood that any of the network service functions maybe associated with policy requirements and/or restrictions. Accordingly,a particular request for service may be accommodated by a first networkslice or a second network slice, with the second slice providing asuperior level of service than the first. Depending upon thepolicies/restrictions, access to the second network slice may berestricted or prohibited. In such instances, one or more of the network,a network operator and/or a service provider can be notified as to therequest, the identified slice(s) and any access restrictions. In someinstances, a modification to the policy and/or authorization or accessrestrictions can be initiated to facilitate a provisioning of theotherwise restricted network slice(s). Such granting of access can beperformed on a temporary basis, e.g., for a limited duration, inassociation with a special event, e.g., a sporting event, an emergencyadaptation, a geo-location, a service availability, and the like.

It is further understood that any granting of access can be accomplishedunilaterally, e.g., without notifying or requiring feedback from asubscriber. Alternatively or in addition, it is contemplated thatgranting of access can be made conditional, e.g., responsive toacceptance of an offer extended to the subscriber to invoke the accessauthorization. For example, a subscriber can request a service andreceive a notification that the request is not supported based on apresent subscription level, or that the request, although supported,could benefit from an enhanced service not currently available based onthe present subscription level. The offer might allow a subscriber tomodify they subscription, e.g., temporarily, for cost, or in associationwith a marketing effort, or the like. In at least some instances,extension of and/or acceptance of the offer can change the subscriber'sSLA in a manner that allows access to the second network slice(s).

The process 300 can receive and change a destination subscriber SLA. Forexample, when a calling party, either prior to call or while talking toa called party can receive an indication of coverage and from asubscriber information repository, such as a Home Subscriber Server(HSS), the subscriber profile, class and/or QoS can be identified forthe particular subscriber, e.g., the called party. The calling and/orcalled party can dynamically pay for an increase the SLA, allowing foror otherwise initiating movement of the call (a call being placed or anexisting call being upgraded) to a superior slice. The superior slicecan be obtained for an improved connection, e.g., for that particularcall only, for a certain period of time or according to some otherrequirement. Such upgrades or modifications can be accomplished for anindividual, or for a family plan. For example, a reporter talking to aprivate subscriber can, while talking, pay for a premiumservice/connection in 5G network to allow the existing service to beupgraded during delivery of the service being upgraded.

It is envisioned that in at least some scenarios, a requested servicedepends upon a policy of a subscriber and/or UE other than therequestor. For example, if a first subscriber requests a service tostream high definition video from the first subscriber's UE to anothersubscriber's UE, the service may require authorization of the second,recipient UE to receive the service. To the extent any policy deficiencyis associated with the second, e.g., recipient party, the offer can beextended to the second subscriber, to the first subscriber, or to boththe first and second subscribers. In some aspects, provisioning ofaccess of the recipient's UE to the requested service is based onacceptance of an offer and/or payment by the first subscriber, e.g., asin a collect toll call. Once the applicable slices have been provisionedor otherwise configured, network traffic, including control plane anduser plane traffic, is forwarded to the selected and/or assignedslice(s) at 316.

FIG. 3B depicts an illustrative embodiment of another processes 340 formanaging network resources used in portions of the system described inFIGS. 1-2.

Network traffic associated with a service requested by a UE, includingcontrol plane and user plane traffic, are forward to a first logicalnetwork slice or group of logical network slices at 342 of acommunication network 100, 200 (FIGS. 1-2). In general, the logicalnetwork slice(s) provide one or more service functions that supportapplication service requirements associated with a service requested bythe UE. Service functions of the selected and/or assigned logicalnetwork slice(s) are identified and compared at 344 to service torequirement(s) and/or preference(s) associated with the requestedservice.

To an extent that a determination is made at 346 that the servicefunctions of the selected/assigned network slices satisfy the servicerequirements/preferences of the requested service, network operationcontinues. Namely, the control plane and user or data plane operationscontinue according to the selected/assigned network slices. However, toan extent that a determination is made at 346 that the service functionsof the selected/assigned network slices do not satisfy the servicerequirements/preferences of the requested service, a second logicalnetwork slice or group of slices is identified at 348.

In some embodiments, a repeating of steps 344 and/or 346 can be doneperiodically, e.g., according to time period. Alternatively or inaddition, the steps 344 and/or 346 can be initiated in response to anevent, such as detection or receipt of a change request, and/ordetermination of an emergency. Still further, one or more of steps 344and 346 can be performed responsive to network conditions, e.g., inresponse to capacity and/or load surpassing some predeterminedthreshold, in response to identification of service availability, UEconditions, UE locations, and the like.

Responsive to identifying the second network slice(s), one or moreprofile(s) and/or policy(s) are identified at 350. Theprofile(s)/policy(s) are associated with one or more of the secondnetwork slice(s), the UE and/or a subscriber identification of the UEthat requested the service. In at least some embodiments, theprofile(s)/policy(s) can include a service type, a QoS and/or asubscriber type, e.g., an enterprise subscriber, an individualsubscriber, a family member subscriber. The profile(s)/policy(s) caninclude exact values, ranges, thresholds, or combinations thereof.

A determination as to whether the profile(s)/policy(s) are satisfied ismade at 352. The determination can be based on one or more of asubscriber identity, a subscriber membership, a level of subscription, aUE type. Alternatively or in addition, whether the profile(s)/policy(s)are satisfied can be based on one or more of a specific event, aspecific location or range of locations, a specific network condition,e.g., capacity and/or load, a time of day, a period of time, a date, anemergency, and the like. To an extent that the profile(s)/policy(s) aresatisfied at 352, network traffic including control plane and data oruser plane operations supporting the requesting UE are exchanged at 358by way of the second network slice(s).

The process 340 can continue from step 344, once again comparingselected/assigned slice(s) service to requirement(s)/preference(s). Itis envisioned that service requirements and/or preferences can change.For example, such changes can occur during an existing service based ona user request, an application requirement, network conditions, or someother factor that results in a disagreement between the servicefunctions provided by the selected/assigned slice(s) and the current,e.g., updated requirement(s)/preference(s).

To an extent that the profile(s)/policy(s) are not satisfied at 352, aprofile and/or policy modification is identified and a determinationmade at 354 as to whether the modification is authorized. To the extentthat the modification is authorized, the profile(s) and/or policy(s) aremodified at 356, and network traffic including control plane and data oruser plane operations supporting the requesting UE are exchanged at 358by way of the second network slice(s). Once again, the process 340 cancontinue from step 344. To the extent that the modification is notauthorized, the profile(s) and/or policy(s) are not modified and theprocess continues from 342, e.g., continuing to forward network trafficaccording to the first selected/assigned network slices.

While for purposes of simplicity of explanation, the respectiveprocesses are shown and described as a series of blocks in FIGS. 3A-3B,it is to be understood and appreciated that the claimed subject matteris not limited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Moreover, not all illustrated blocks maybe required to implement the methods described herein.

FIG. 4 depicts an illustrative embodiment of a communication system 400for providing various communication services, such as delivering mediacontent. The communication system 400 can represent an interactive medianetwork, such as an interactive television system (e.g., an InternetProtocol Television (IPTV) media system). Communication system 400 canbe overlaid or operably coupled with the communication networks 100, 200of FIGS. 1 and/or 2 as another representative embodiment ofcommunication system 400. For instance, one or more devices illustratedin the communication system 400 of FIG. 4, can participate in deliveryof a multi-slicing on demand capability, allowing one or more UEsplanning or otherwise engaging in a particular service to access, modifyor otherwise change a configuration of logical network slices supportingthe particular service.

In one or more embodiments, the communication system 400 can include asuper head-end office (SHO) 410 with at least one super headend officeserver (SHS) 411 which receives media content from satellite and/orterrestrial communication systems. In the present context, media contentcan represent, for example, audio content, moving image content such as2D or 3D videos, video games, virtual reality content, still imagecontent, and combinations thereof. The SHS server 411 can forwardpackets associated with the media content to one or more video head-endservers (VHS) 414 via a network of video head-end offices (VHO) 412according to a multicast communication protocol. The VHS 414 candistribute multimedia broadcast content via an access network 418 tocommercial and/or residential buildings 402 housing a gateway 404 (suchas a residential or commercial gateway).

The access network 418 can represent a group of digital subscriber lineaccess multiplexers (DSLAMs) located in a central office or a servicearea interface that provide broadband services over fiber optical linksor copper twisted pairs 419 to buildings 402. The gateway 404 can usecommunication technology to distribute broadcast signals to mediaprocessors 406 such as Set-Top Boxes (STBs) which in turn presentbroadcast channels to media devices 408 such as computers or televisionsets managed in some instances by a media controller 407 (such as aninfrared or RF remote controller).

The gateway 404, the media processors 406, and media devices 408 canutilize tethered communication technologies (such as coaxial, powerlineor phone line wiring) or can operate over a wireless access protocolsuch as Wireless Fidelity (WiFi), Bluetooth®, Zigbee®, or other presentor next generation local or personal area wireless network technologies.By way of these interfaces, unicast communications can also be invokedbetween the media processors 406 and subsystems of the IPTV media systemfor services such as video-on-demand (VoD), browsing an electronicprogramming guide (EPG), or other infrastructure services.

A satellite broadcast television system 429 can be used in the mediasystem of FIG. 4. The satellite broadcast television system can beoverlaid, operably coupled with, or replace the IPTV system as anotherrepresentative embodiment of communication system 400. In thisembodiment, signals transmitted by a satellite 415 that include mediacontent can be received by a satellite dish receiver 431 coupled to thebuilding 402. Modulated signals received by the satellite dish receiver431 can be transferred to the media processors 406 for demodulating,decoding, encoding, and/or distributing broadcast channels to the mediadevices 408. The media processors 406 can be equipped with a broadbandport to an Internet Service Provider (ISP) network 432 to enableinteractive services such as VoD and EPG as described above.

In yet another embodiment, an analog or digital cable broadcastdistribution system such as cable TV system 433 can be overlaid,operably coupled with, or replace the IPTV system and/or the satelliteTV system as another representative embodiment of communication system400. In this embodiment, the cable TV system 433 can also provideInternet, telephony, and interactive media services. System 400 enablesvarious types of interactive television and/or services including IPTV,cable and/or satellite.

The subject disclosure can apply to other present or next generationover-the-air and/or landline media content services system.

Some of the network elements of the IPTV media system can be coupled toone or more computing devices 430, a portion of which can operate as aweb server for providing web portal services over the ISP network 432 towireline media devices 408 or wireless communication devices 416.

Communication system 400 can also provide for all or a portion of thecomputing devices 430 to function as a multi-slicing server (hereinreferred to as multi-slicing server 430). The multi-slicing server 430can use computing and communication technology to perform function 462,which can include among other things, the multi-slicing techniquesdescribed by processes 300, 340 of FIGS. 3A-B. For instance, function462 of multi-slicing server 430 can be similar to the functionsdescribed for SDN controller 130-145, 210, the service layer 125, 208,the management gateways 142, 204 of FIGS. 1-2 in accordance with process300. The media processors 406 and wireless communication devices 416 canbe provisioned with software functions 464 and 465, respectively, toutilize the services of multi-slicing server 430. For instance,functions 464 and 465 of media processors 406 and wireless communicationdevices 416 can be similar to the functions described for thecommunication devices 116, 202 of FIGS. 1-2 in accordance with theprocess 300 of FIG. 3.

Multiple forms of media services can be offered to media devices overlandline technologies such as those described above. Additionally, mediaservices can be offered to media devices by way of a wireless accessbase station 417 operating according to common wireless access protocolssuch as Global System for Mobile or GSM, Code Division Multiple Accessor CDMA, Time Division Multiple Access or TDMA, Universal MobileTelecommunications or UMTS, World interoperability for Microwave orWiMAX, Software Defined Radio or SDR, Long Term Evolution or LTE, and soon. Other present and next generation wide area wireless access networktechnologies can be used in one or more embodiments of the subjectdisclosure.

FIG. 5 depicts an illustrative embodiment of a communication system 500employing an IP Multimedia Subsystem (IMS) network architecture tofacilitate the combined services of circuit-switched and packet-switchedsystems. Communication system 500 can be overlaid or operably coupledwith systems 100, 200 of FIGS. 1 and/or 2 and communication system 400as another representative embodiment of communication system 400. Forinstance, one or more devices illustrated in the communication system500 of FIG. 5, can participate in delivery of a multi-slicing on demandcapability, allowing one or more UEs planning or otherwise engaging in aparticular service to access, modify or otherwise change a configurationof logical network slices supporting the particular service.

Communication system 500 can comprise a Home Subscriber Server (HSS)540, a tElephone NUmber Mapping (ENUM) server 530, and other networkelements of an IMS network 550. The IMS network 550 can establishcommunications between IMS-compliant communication devices (CDs) 501,502, Public Switched Telephone Network (PSTN) CDs 503, 505, andcombinations thereof by way of a Media Gateway Control Function (MGCF)520 coupled to a PSTN network 560. The MGCF 520 need not be used when acommunication session involves IMS CD to IMS CD communications. Acommunication session involving at least one PSTN CD may utilize theMGCF 520.

IMS CDs 501, 502 can register with the IMS network 550 by contacting aProxy Call Session Control Function (P-CSCF) which communicates with aninterrogating CSCF (I-CSCF), which in turn, communicates with a ServingCSCF (S-CSCF) to register the CDs with the HSS 540. To initiate acommunication session between CDs, an originating IMS CD 501 can submita Session Initiation Protocol (SIP INVITE) message to an originatingP-CSCF 504 which communicates with a corresponding originating S-CSCF506. The originating S-CSCF 506 can submit the SIP INVITE message to oneor more application servers (ASs) 517 that can provide a variety ofservices to IMS subscribers.

For example, the application servers 517 can be used to performoriginating call feature treatment functions on the calling party numberreceived by the originating S-CSCF 506 in the SIP INVITE message.Originating treatment functions can include determining whether thecalling party number has international calling services, call IDblocking, calling name blocking, 7-digit dialing, and/or is requestingspecial telephony features (e.g., *72 forward calls, *73 cancel callforwarding, *67 for caller ID blocking, and so on). Based on initialfilter criteria (iFCs) in a subscriber profile associated with a CD, oneor more application servers may be invoked to provide various calloriginating feature services.

Additionally, the originating S-CSCF 506 can submit queries to the ENUMsystem 530 to translate an E.164 telephone number in the SIP INVITEmessage to a SIP Uniform Resource Identifier (URI) if the terminatingcommunication device is IMS-compliant. The SIP URI can be used by anInterrogating CSCF (I-CSCF) 507 to submit a query to the HSS 540 toidentify a terminating S-CSCF 514 associated with a terminating IMS CDsuch as reference 502. Once identified, the I-CSCF 507 can submit theSIP INVITE message to the terminating S-CSCF 514. The terminating S-CSCF514 can then identify a terminating P-CSCF 516 associated with theterminating CD 502. The P-CSCF 516 may then signal the CD 502 toestablish Voice over Internet Protocol (VoIP) communication services,thereby enabling the calling and called parties to engage in voiceand/or data communications. Based on the iFCs in the subscriber profile,one or more application servers may be invoked to provide various callterminating feature services, such as call forwarding, do not disturb,music tones, simultaneous ringing, sequential ringing, etc.

In some instances the aforementioned communication process issymmetrical. Accordingly, the terms “originating” and “terminating” inFIG. 5 may be interchangeable. It is further noted that communicationsystem 500 can be adapted to support video conferencing. In addition,communication system 500 can be adapted to provide the IMS CDs 501, 502with the multimedia and Internet services of communication system 400 ofFIG. 4.

If the terminating communication device is instead a PSTN CD such as CD503 or CD 505 (in instances where the cellular phone only supportscircuit-switched voice communications), the ENUM system 530 can respondwith an unsuccessful address resolution which can cause the originatingS-CSCF 506 to forward the call to the MGCF 520 via a Breakout GatewayControl Function (BGCF) 519. The MGCF 520 can then initiate the call tothe terminating PSTN CD over the PSTN network 560 to enable the callingand called parties to engage in voice and/or data communications.

It is further appreciated that the CDs of FIG. 5 can operate as wirelineor wireless devices. For example, the CDs of FIG. 5 can becommunicatively coupled to a cellular base station 521, a femtocell, aWiFi router, a Digital Enhanced Cordless Telecommunications (DECT) baseunit, or another suitable wireless access unit to establishcommunications with the IMS network 550 of FIG. 5. The cellular accessbase station 521 can operate according to common wireless accessprotocols such as GSM, CDMA, TDMA, UMTS, WiMax, SDR, LTE, and so on.Other present and next generation wireless network technologies can beused by one or more embodiments of the subject disclosure. Accordingly,multiple wireline and wireless communication technologies can be used bythe CDs of FIG. 5.

Cellular phones supporting LTE can support packet-switched voice andpacket-switched data communications and thus may operate asIMS-compliant mobile devices. In this embodiment, the cellular basestation 521 may communicate directly with the IMS network 550 as shownby the arrow connecting the cellular base station 521 and the P-CSCF516.

Alternative forms of a CSCF can operate in a device, system, component,or other form of centralized or distributed hardware and/or software.Indeed, a respective CSCF may be embodied as a respective CSCF systemhaving one or more computers or servers, either centralized ordistributed, where each computer or server may be configured to performor provide, in whole or in part, any method, step, or functionalitydescribed herein in accordance with a respective CSCF. Likewise, otherfunctions, servers and computers described herein, including but notlimited to, the HSS, the ENUM server, the BGCF, and the MGCF, can beembodied in a respective system having one or more computers or servers,either centralized or distributed, where each computer or server may beconfigured to perform or provide, in whole or in part, any method, step,or functionality described herein in accordance with a respectivefunction, server, or computer.

The multi-slicing server 430 of FIG. 4 can be operably coupled tocommunication system 500 for purposes similar to those described above.Multi-slicing server 430 can perform function 462 and thereby providemulti-slicing services to the CDs 501, 502, 503 and 505 of FIG. 5similar to the functions described for one or more of the SDN controller210, the service layer 208 and the management gateway 204 of FIG. 2 inaccordance with processes 300, 340 of FIGS. 3A-B. CDs 501, 502, 503 and505, which can be adapted with software to perform function 572 toutilize the services of the multi-slicing server 430 similar to thefunctions described for the SDN controller 130-145, 210, the servicelayer 125, 208 and the management gateways 142, 204 of FIGS. 1-2 inaccordance with the processes 300, 340 of FIGS. 3A-B. The multi-slicingserver 430 can be an integral part of the application server(s) 517performing function 574, which can be substantially similar to function462 and adapted to the operations of the IMS network 550.

For illustration purposes only, the terms S-CSCF, P-CSCF, I-CSCF, and soon, can be server devices, but may be referred to in the subjectdisclosure without the word “server.” It is also understood that anyform of a CSCF server can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as DIAMETER commandsare terms can include features, methodologies, and/or fields that may bedescribed in whole or in part by standards bodies such as 3^(rd)Generation Partnership Project (3GPP). It is further noted that some orall embodiments of the subject disclosure may in whole or in partmodify, supplement, or otherwise supersede final or proposed standardspublished and promulgated by 3GPP.

FIG. 6 depicts an illustrative embodiment of a web portal 602 of acommunication system 600. Communication system 600 can be overlaid oroperably coupled with systems 100-200 of FIGS. 1 and/or 2, communicationsystem 400, and/or communication system 500 as another representativeembodiment of systems 100, 200 of FIGS. 1 and/or 2, communication system400, and/or communication system 500. The web portal 602 can be used formanaging services of systems 100, 200 of FIGS. 1 and/or 2 andcommunication systems 400-500. A web page of the web portal 602 can beaccessed by a Uniform Resource Locator (URL) with an Internet browserusing an Internet-capable communication device such as those describedin FIGS. 1 and/or 2 and FIGS. 4-5. The web portal 602 can be configured,for example, to access a media processor 406 and services managedthereby such as a Digital Video Recorder (DVR), a Video on Demand (VoD)catalog, an Electronic Programming Guide (EPG), or a personal catalog(such as personal videos, pictures, audio recordings, etc.) stored atthe media processor 406. The web portal 602 can also be used forprovisioning IMS services described earlier, provisioning Internetservices, provisioning cellular phone services, and so on.

The web portal 602 can further be utilized to manage and provisionsoftware applications 462-466, and 572-574 to adapt these applicationsas may be desired by subscribers and/or service providers of systems100, 200 of FIGS. 1 and/or 2, and communication systems 400-500. Forinstance, users of the services provided by multi-slicing server 430 canlog into their on-line accounts and provision the servers 110 or server430 with profile information, subscription information, enterprisemembers, family members, authorization information, conditions, etc.,that a user, e.g., a subscriber and/or a provider may want to programsuch as user profiles, provide contact information to server to enableit to communication with devices described in FIGS. 1-5, and so on.Service providers can log onto an administrator account to provision,monitor and/or maintain the systems 100, 200 of FIGS. 1 and/or 2 orserver 430.

FIG. 7 depicts an illustrative embodiment of a communication device 700.Communication device 700 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1 and/or 2, andFIGS. 4-5 and can be configured to perform at least portions of theprocess 300 of FIG. 3.

Communication device 700 can comprise a wireline and/or wirelesstransceiver 702 (herein transceiver 702), a user interface (UI) 704, apower supply 714, a location receiver 716, a motion sensor 718, anorientation sensor 720, and a controller 706 for managing operationsthereof. The transceiver 702 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, orcellular communication technologies, just to mention a few (Bluetooth®and ZigBee® are trademarks registered by the Bluetooth® Special InterestGroup and the ZigBee® Alliance, respectively). Cellular technologies caninclude, for example, CDMA-1×, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,WiMAX, SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 702 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof.

The UI 704 can include a depressible or touch-sensitive keypad 708 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device700. The keypad 708 can be an integral part of a housing assembly of thecommunication device 700 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth®. The keypad 708 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 704 can further include a display710 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 700. In anembodiment where the display 710 is touch-sensitive, a portion or all ofthe keypad 708 can be presented by way of the display 710 withnavigation features.

The display 710 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 700 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 710 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 710 can be an integral part of thehousing assembly of the communication device 700 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 704 can also include an audio system 712 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 712 can further include amicrophone for receiving audible signals of an end user. The audiosystem 712 can also be used for voice recognition applications. The UI704 can further include an image sensor 713 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 714 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 700 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 716 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 700 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 718can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 700 in three-dimensional space. Theorientation sensor 720 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device700 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 700 can use the transceiver 702 to alsodetermine a proximity to a cellular, WiFi, Bluetooth®, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 706 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 700.

Other components not shown in FIG. 7 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 700 can include a reset button (not shown). The reset button canbe used to reset the controller 706 of the communication device 700. Inyet another embodiment, the communication device 700 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 700 to force thecommunication device 700 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 700 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 700 as described herein can operate with moreor less of the circuit components shown in FIG. 7. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 700 can be adapted to perform the functions ofdevices of FIGS. 1 and/or 2, the media processor 406, the media devices408, or the portable communication devices 416 of FIG. 4, as well as theIMS CDs 501-502 and PSTN CDs 503-505 of FIG. 5. It will be appreciatedthat the communication device 700 can also represent other devices thatcan operate in systems 100, 200 of FIGS. 1 and/or 2, communicationsystems 400-500 of FIGS. 4-5 such as a gaming console and a mediaplayer. In addition, the controller 706 can be adapted in variousembodiments to perform the functions 462-466 and 572-574, respectively.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. For example, one or more of the communicationdevices, e.g., UE, can be configured with an application that can beused to coordinate, activate and/or otherwise manage access tomulti-slicing on demand features disclosed herein. Such a mobileapplication can support in-service upgrades, access to a portal tomodify profiles, preferences, and the like. Other embodiments can beused in the subject disclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 8 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 800 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the multi-slicing server 430, the mediaprocessor 406, the SDN controllers 130-145, 210, the service layer 125,208, the management gateways 142, 204, the access networks 117, 205, theapplication server 222, a storage device or service 224, generalcomputing hardware supporting one or more of the various VNFs disclosedherein, including VNFs 214, 216, and other devices of FIGS. 1-2 and 4-5.In some embodiments, the machine may be connected (e.g., using a network826) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 800 may include a processor (or controller) 802(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 804 and a static memory 806, whichcommunicate with each other via a bus 808. The computer system 800 mayfurther include a display unit 810 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 800may include an input device 812 (e.g., a keyboard), a cursor controldevice 814 (e.g., a mouse), a disk drive unit 816, a signal generationdevice 818 (e.g., a speaker or remote control) and a network interfacedevice 820. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units810 controlled by two or more computer systems 800. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 810, while the remainingportion is presented in a second of the display units 810.

The disk drive unit 816 may include a tangible computer-readable storagemedium 822 on which is stored one or more sets of instructions (e.g.,software 824) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above. Theinstructions 824 may also reside, completely or at least partially,within the main memory 804, the static memory 806, and/or within theprocessor 802 during execution thereof by the computer system 800. Themain memory 804 and the processor 802 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. Distributedprocessing environments can include multiple processors in a singlemachine, single processors in multiple machines, and/or multipleprocessors in multiple machines. It is further noted that a computingdevice such as a processor, a controller, a state machine or othersuitable device for executing instructions to perform operations ormethods may perform such operations directly or indirectly by way of oneor more intermediate devices directed by the computing device.

While the tangible computer-readable storage medium 822 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, WiFi, Zigbee®), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 800. In one or more embodiments, information regardinguse of services can be generated including services being accessed,media consumption history, user preferences, and so forth. Thisinformation can be obtained by various methods including user input,detecting types of communications (e.g., video content vs. audiocontent), analysis of content streams, and so forth. The generating,obtaining and/or monitoring of this information can be responsive to anauthorization provided by the user. In one or more embodiments, ananalysis of data can be subject to authorization from user(s) associatedwith the data, such as an opt-in, an opt-out, acknowledgementrequirements, notifications, selective authorization based on types ofdata, and so forth.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A device, comprising: a processing systemincluding a processor; and a memory that stores executable instructionsthat, when executed by the processing system, facilitate performance ofoperations, the operations comprising: facilitating an association of afirst user data traffic flow with a first logical network slice of amobile network, the first user data traffic flow being conveyed by thefirst logical network slice and associated with a mobile application ofa first mobile device contemporaneously accessing a first servicefunction and a second service function via the mobile network; andfacilitating an association of a second user data traffic flow with asecond logical network slice of the mobile network, wherein the seconduser data traffic flow is conveyed by the second logical network slicecontemporaneously with conveyance of the first user data traffic flow bythe first logical network slice, and wherein the first user data trafficflow conveyed by the first logical network slice is isolated from thesecond user data traffic flow conveyed by the second logical networkslice.
 2. The device of claim 1, wherein the operations furthercomprise: determining that the first service function and the secondservice function be associated with different logical network slices ofthe mobile network, wherein the facilitating of the association of thesecond user data traffic flow with the second logical network slice isresponsive to the determining that the first service function and thesecond service function be associated with different logical networkslices.
 3. The device of claim 2, wherein the operations furthercomprise: receiving a request to facilitate provisioning of the firstservice function and the second service function, wherein thedetermining that the first service function and the second servicefunction be associated with different logical network slices isresponsive to the request.
 4. The device of claim 1, wherein theoperations further comprise: determining whether access credentialsassociated with the first mobile device satisfy access requirements ofthe second logical network slice, wherein the facilitating of theassociation of the second user data traffic flow with the second logicalnetwork slice is based on a determination that the access credentialssatisfy the access requirements.
 5. The device of claim 4, wherein theoperations further comprise: responsive to a determination that theaccess credentials do not satisfy the access requirements: facilitatinga modification of the access credentials of the first mobile device toobtain modified access credentials, wherein the facilitating of theassociation of the second user data traffic flow with the second logicalnetwork slice of the mobile network is based on the modified accesscredentials satisfying the access requirements.
 6. The device of claim5, wherein the facilitating of the modification of the accesscredentials further comprises a temporary modification that satisfiesthe access requirements for a limited period of time.
 7. The device ofclaim 6, wherein the limited period of time is based on one of aspecified call, a predetermined period of time, occurrence of an event,a location, a time of day, or a combination thereof.
 8. The device ofclaim 1, wherein the first service function and the second servicefunction differ according to one of a service type, a quality of servicefunction, a subscriber type, or a combination thereof.
 9. A method,comprising: facilitating, by a processing system including a processor,an association of a first user data traffic flow with a first networkslice of a network, wherein the first user data traffic flow is conveyedby the first network slice and associated with a mobile application of afirst device contemporaneously accessing a first service function and asecond service function via the network; and facilitating, by theprocessing system, an association of a second user data traffic flowwith a second network slice of the network, the second user data trafficflow being conveyed by the second network slice contemporaneously withconveyance of the first user data traffic flow by the first networkslice, and wherein the first user data traffic flow is isolated from thesecond user data traffic flow.
 10. The method of claim 9, furthercomprising: determining, by the processing system, that the firstservice function and the second service function be associated withdifferent network slices of the network, wherein the facilitating of theassociation of the second user data traffic flow with the second networkslice is responsive to the determining that the first service functionand the second service function be associated with different networkslices.
 11. The method of claim 10, further comprising: receiving, bythe processing system, a request to facilitate provisioning of the firstservice function and the second service function, wherein thedetermining that the first service function and the second servicefunction be associated with different network slices is responsive tothe request.
 12. The method of claim 9, further comprising: determining,by the processing system, whether access credentials associated with thefirst device satisfy access requirements of the second network slice,wherein the facilitating of the association of the second user datatraffic flow with the second network slice is based on a determinationthat the access credentials satisfy the access requirements.
 13. Themethod of claim 12, further comprising: responsive to a determinationthat the access credentials do not satisfy the access requirements:facilitating, by the processing system, a modification of the accesscredentials of the first device to obtain modified access credentials,wherein the facilitating of the association of the second user datatraffic flow with the second network slice of the network is based onthe modified access credentials satisfying the access requirements. 14.The method of claim 13, wherein the facilitating of the modification ofthe access credentials comprises a temporary modification that satisfiesthe access requirements for a limited period of time.
 15. The method ofclaim 14, wherein the limited period of time is based on one of aspecified call, a predetermined period of time, occurrence of an event,a location, a time of day, or a combination thereof.
 16. Anon-transitory, machine-readable storage medium, comprising executableinstructions that, when executed by a processing system including aprocessor, facilitate performance of operations, the operationscomprising: facilitating an association of a first user data trafficflow with a first logical network slice of a communication network,wherein the first user data traffic flow is conveyed by the firstlogical network slice and associated with an application of a firstcommunication device contemporaneously accessing a first servicefunction and a second service function via the communication network;and facilitating an association of a second user data traffic flow witha second logical network slice of the communication network, the seconduser data traffic flow being conveyed by the second logical networkslice contemporaneously with conveyance of the first user data trafficflow by the first logical network slice, and wherein the first user datatraffic flow is isolated from the second user data traffic flow.
 17. Thenon-transitory, machine-readable storage medium of claim 16, wherein theoperations further comprise: determining that the first service functionand the second service function be associated with different logicalnetwork slices of the communication network, wherein the facilitating ofthe association of the second user data traffic flow with the secondlogical network slice is responsive to the determining that the firstservice function and the second service function be associated withdifferent logical network slices.
 18. The non-transitory,machine-readable storage medium of claim 17, wherein the operationsfurther comprise: receiving a request to facilitate provisioning of thefirst service function and the second service function, wherein thedetermining that the first service function and the second servicefunction be associated with different logical network slices isresponsive to the request.
 19. The non-transitory, machine-readablestorage medium of claim 16, wherein the operations further comprise:determining whether access credentials associated with the firstcommunication device satisfy access requirements of the second logicalnetwork slice, wherein the facilitating of the association of the seconduser data traffic flow with the second logical network slice is based ona determination that the access credentials satisfy the accessrequirements.
 20. The non-transitory, machine-readable storage medium ofclaim 19, wherein the operations further comprise: responsive to adetermination that the access credentials do not satisfy the accessrequirements: facilitating a modification of the access credentials ofthe first communication device to obtain modified access credentials,wherein the facilitating of the association of the second user datatraffic flow with the second logical network slice of the communicationnetwork is based on the modified access credentials satisfying theaccess requirements.